Blockchain driven embedded video and digital signatures on signed documents

ABSTRACT

Systems, devices and methods are provided for blockchain driven embedded video and digital signatures on signed documents. The present disclosure includes providing a video conference initiated with the process of signing a document. The video conference and the signing process and the video are recorded. The recorded video captures all conversations, understanding and the final signing by participants. Both the signature and the recorded signing event in video conference are stored with a hash value as a blockchain.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 17/339,892, filed Jun. 4, 2021, which claims priority to U.S.Provisional Application No. 63/036,441, filed Jun. 8, 2020, thedisclosures of which are hereby incorporated by reference in theirentirety for all purposes.

FIELD

Embodiments of the present disclosure generally relate to digitalsignatures on documents, and more specifically to blockchain drivenembedded video and digital signatures on signed documents.

BACKGROUND

The main problem with digital signing today is it is “impersonal”. Todaythe esign solutions are single dimensional, impersonal and error prone.First people do not read what they sign all the time and signmechanically. Second the authentication of the signer is done via emailand there is no visual confirmation that the signer is “who this personis”.

Thus, there is a need for a digital signature (esign) technologyproviding interactive digital signatures on signed documents withauthentication, the technology can use blockchain driven embedded videoand digital signatures on signed documents, without the abovedisadvantages and provides other advantages as described herein.

SUMMARY

In general, the present disclosure can include providing a videoconference initiated with the process of signing a document to make theprocess personal, and the sender of the document can verify visually whois signing. The video conference and the signing process can occur in aninvited virtual room session, and the video can be recorded. Therecorded video can capture all conversations, understanding and thefinal signing by participants. In some embodiments, both the signatureand the recorded signing event in video conference can be stored with ahash value as a blockchain to make the stored data completely immutable.

In some embodiments, the present disclosure can include acomputer-implemented method for blockchain driven embedded video anddigital signature on a signed document, the method comprising: receivinga document for digital signature; receiving input indicating one or morelocations or markers for digital signature; receiving input indicatingvideo requirement for the signed document; sending a digital link to auser, wherein the digital link is configured to load a digital documentand a videoconference session; receiving a digital signature for each ofthe one or more locations; receiving a video of the videoconferencesession; generating a hash value for the signed document and the video;storing the video, the signed document and the hash value; and updatinga blockchain including the video, the signed document and the hashvalue.

In some embodiments, the present disclosure can also includecomputer-implemented method for hash-based embedded video and digitalsignature on a signed document, the method comprising: receiving adocument for digital signature; receiving input indicating one or morelocations for digital signature; receiving input indicating videorequirement for the signed document; sending a digital link to a user,wherein the digital link is configured to load a digital document and avideoconference session; receiving a digital signature for each of theone or more locations; receiving a video of the videoconference session;generating a hash value for the signed document and the video; andstoring the video, the signed document and the hash value.

This summary and the following detailed description are merelyexemplary, illustrative, and explanatory, and are not intended to limit,but to provide further explanation of the invention as claimed.Additional features and advantages of the invention will be set forth inthe descriptions that follow, and in part will be apparent from thedescription, or can be learned by practice of the invention. Theobjectives and other advantages of the invention will be realized andattained by the structure particularly pointed out in the writtendescription, claims and the appended drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood by referring to thefollowing figures. The components in the figures are not necessarily toscale. Emphasis instead being placed upon illustrating the principles ofthe disclosure. In the figures, reference numerals designatecorresponding parts throughout the different views.

FIG. 1 shows an example process to provide blockchain driven embeddedvideo and digital signatures on signed documents, according to someembodiments of the present disclosure.

FIG. 2 shows an exemplary high-level backend topology, according to someembodiments of the present disclosure.

FIG. 3 shows an exemplary overall platform for various embodiments andprocess steps, according to some embodiments of the present disclosure.

FIGS. 4 to 17 show exemplary user interfaces of the present disclosure.

DETAILED DESCRIPTIONS

The following disclosure describes various embodiments of the presentinvention and method of use in at least one of its preferred, best modeembodiments, which is further defined in detail in the followingdescription. Those having ordinary skill in the art may be able to makealterations and modifications to what is described herein withoutdeparting from its spirit and scope. While this invention is susceptibleto different embodiments in different forms, there is shown in thedrawings and will herein be described in detail a preferred embodimentof the invention with the understanding that the present disclosure isto be considered as an exemplification of the principles of theinvention and is not intended to limit the broad aspect of the inventionto the embodiment illustrated. All features, elements, components,functions, and steps described with respect to any embodiment providedherein are intended to be freely combinable and substitutable with thosefrom any other embodiment unless otherwise stated. Therefore, it shouldbe understood that what is illustrated is set forth only for thepurposes of example and should not be taken as a limitation on the scopeof the present invention.

As used herein and in the appended claims, the singular forms “a,” “an,”and “the” include plural referents unless the context clearly dictatesotherwise.

In general, terms such as “coupled to,” and “configured for couplingto,” and “secure to,” and “configured for securing to” and “incommunication with” (for example, a first component is “coupled to” or“is configured for coupling to” or is “configured for securing to” or is“in communication with” a second component) are used herein to indicatea structural, functional, mechanical, electrical, signal, optical,magnetic, electromagnetic, ionic or fluidic relationship between two ormore components or elements. As such, the fact that one component issaid to be in communication with a second component is not intended toexclude the possibility that additional components may be presentbetween, and/or operatively associated or engaged with, the first andsecond components.

In the following description and in the figures, like elements areidentified with like reference numerals. The use of “e.g.,” “etc.,” and“or” indicates non-exclusive alternatives without limitation, unlessotherwise noted. The use of “including” or “includes” means “including,but not limited to,” or “includes, but not limited to,” unless otherwisenoted.

As used herein, the term “and/or” placed between a first entity and asecond entity means one of (1) the first entity, (2) the second entity,and (3) the first entity and the second entity. Multiple entities listedwith “and/or” should be construed in the same manner, i.e., “one ormore” of the entities so conjoined. Other entities may optionally bepresent other than the entities specifically identified by the “and/or”clause, whether related or unrelated to those entities specificallyidentified. Thus, as a non-limiting example, a reference to “A and/orB,” when used in conjunction with open-ended language such as“comprising” can refer, in one embodiment, to A only (optionallyincluding entities other than B); in another embodiment, to B only(optionally including entities other than A); in yet another embodiment,to both A and B (optionally including other entities). These entitiesmay refer to elements, actions, structures, steps, operations, values,and the like.

Provided herein are example embodiments of system, apparatus and methodto provide blockchain driven embedded video and digital signatures onsigned documents. The present disclosure includes practical applicationfor and improving, among others, technologies for digital recordsmanagement, tracking, and authentication, and technologies forcollaboration and authentication of documentation.

An exemplary process 100 of the present disclosure is partly shown inFIG. 1. In this example, the process can include steps to provide for auser to prepare a document for signing. In some implementations, theprocess can include using an application (or App) of the presentdisclosure, which can be either desktop or mobile (an iOS-sampleinstantiation is shown below).

In some embodiments, at step 102, the process can include receiving auser's sign-in (or sign-up if new user), for example, for the serviceprovided by the process. In the example of FIG. 1, the user is someonewho has document(s) that needs to be signed. At step 104, the processcan include receiving one or more document, which needs to be signed,from the user. In some implementations, also as shown in FIG. 5, theuser (or a designated person or persons) can prepare a “bundle” fore-signing by selecting and uploading multiple documents from internalsources (e.g., PC, laptop, phone, etc.) or by integrating externaldrives (Dropbox, Google, Files, Gallery etc.). As used herein, a bundleis a set of documents needing signature.

In some embodiments, after receiving the documents, by reference number105, the process can include determining that only a single person needsto sign the document(s). For example, the user can specify only oneperson as signee. In some embodiments, the user can prepare the signingprocess by selecting a signer (or participant) for signing from abuilt-in contact manager (e.g., phone contacts) or entering name/emailaddress manually. The left side reference number 110 of the flow diagramshows an exemplary “Single Signer” process. For example, at step 112,the single signer can sign in (or sign up, if new user). At step 113,the process can include the user dragging and dropping the documents(s)to the user's local device for editing and/or setting up. At step 114,also as shown in FIG. 7, process can include the user indicating, orsetting up, the locations or markers in the document(s) where the signercan sign, initial, and date. For example, a GUI can be provided for theuser to drag a Signature (or an Initial) box from a menu and drop itinto a location where the signer can sign. At step 115, the process caninclude sending, e.g., via email, SMS, Slack or any suitable form ofonline notification/communication channel, the set-up document(s) to thesigner. In some implementations, the user can announce to the signer viaan app that a set of document(s) is coming their way for signing andsubmitting. In some implementations, the system can allow the signer tosign, initial and date the document(s) digitally.

In some implementations, after receiving the set-up document(s), theprocess can include validating and verifying that the document(s) arefully and correctly set up. The process can then include determiningwhether, by reference number 116, to invite the signer to avideoconference. A videoconference can show and record the signersigning the document(s). If no videoconference is needed or requested,by reference number 117, the process can include receiving the signeddocument(s) from the signer.

Back to step 104, after receiving the documents, by reference number106, the process can include determining that multiple person(s) willneed sign the document(s). In some embodiments, the user can prepare thesigning process by selecting multiple signers (or participants) forsigning from a built-in contact manager (e.g., phone contacts) orentering names/email addresses manually. The right side, by referencenumber 120, of the flow diagram shows and exemplary “Multiple Signers”process. For example, at step 122, the process can include the useradding multiple people as designated signers to the document(s). In someembodiments, the system can present to the user a user interface to addsigners. The GUI can allow the user to indicate whether the signers cansign in sequence, or in parallel. At step 123, the process can includethe user dragging and dropping the documents(s) to the user's localdevice for editing and/or setting up. At step 124, also as shown in FIG.7, process can include the user indicating, or setting up, the locationsor markers in the document(s) where each signer can sign, initial, anddate. In some implementations, after receiving the set-up document(s),the process can include validating and verifying that the document(s)are fully and correctly set up. At step 125, the process can includesending, e.g., via email, the set-up document(s) to each signer. In someimplementations, the user can announce to the signers (or participants)via an app that a set of documents is coming their way for signing.

The process can then include determining whether, by reference number130, to invite the signers to a videoconference. A videoconference canshow and record the signers signing the document(s).

If no videoconference is needed or specified, at step 126, the processcan include each signer receiving and accessing the set-up document(s).In some implementations, the signers can access (or open) thedocument(s) by clicking on a link included in the email sent to thesigners. At step 127, after accessing the document(s), the signer cansign them. In some implementations, the system can allow the signer tosign, initial and date the document(s) digitally, for example, rightinside the accessed (opened) document(s).

At step 128, after each signer signs the document(s), the process caninclude the signer submitting the signed document(s) to the system, forexample, by clicking on a Done button.

Back to step 125, if the user set up the document(s) as havingvideoconference, at the time the system sends an email to each signerwith the link to the document(s), by reference number 130, the link canalso cause the system to initiate a videoconference at step 142, forexample, using Zoom™, Microsoft Team™, Google Meet™, and the like. Atstep 143, the process can include the signers joining thevideoconference and the user, as well as the signers, can witness eachsigner signs the document(s). The videoconference can also provide forsigner collaborations so that the participants can ask any questions orclarification during signing. All conversations, understanding and thefinal signing are recorded. Participants can be in the same room or bein different locations remotely.

The videoconference is recorded by default.

Back to step 115, if the user set up the document(s) as havingvideoconference, at the time the system sends an email to the signerwith the link to the document(s), by reference number 116, the link canalso cause the system to initiate a videoconference at step 142.

At step 144, after the signed document(s) have been received by thesystem, and the videoconference recording is complete, the process canthe include the system storing (saving) the videoconference recording ofthe signing process (video/audio) as a video media and storing thesigned document(s). The system can also generate all the necessarydigital certificate attachments to the signatures. The system can alsogenerate a hash function of the recorded video. The hash value can bestored as part of the digital signing on the document. The hash valuethus makes the document ready to be part of a blockchain, in someembodiments. In some implementations, as shown in FIG. 16 example, thestored video can be accessed by clicking a video link displayed with acompleted bundle.

An example hash function can be implemented via a code like below:

import hashlib BLOCKSIZE = 65536 hasher = hashlib.md5( ) withopen(‘anotherfile.txt’, ‘rb’) as afile:  buf = afile.read(BLOCKSIZE) while len(buf) > 0:   hasher.update(buf)   buf = afile.read(BLOCKSIZE)print(hasher.hexdigest( ))

Note that any other suitable coding language can also be used.

In some embodiments, a hash can be a one-way hash or many other hashfunctions commercially available. It can take a few seconds to generatethe hash from the streamed video.

At step 145, the process can include binding the digital signature tothe document using, for example, digital certificate. If the signingprocess includes videoconference, the process can include fetching thehash value of the video and bind the video and the digital signature tothe document using, for example, digital certificate.

In some embodiments, the Digital Certificate can be used when thesignatures are saved in a PDF using a public/private key standardencryption. The digital certificate which is used for the signingenables this and its root link can be traced by any PDF reader tool. Thedigital certificate can be stored under a SOC 2 compliance high securitydata server, for example, at MSFT Azure or Amazon (AWS) like data undera HSM box (hardware security module). This digital certificate is nontamperable and together with Advanced PDF engineering standardsimplemented in the system, a PDF reader can validate the authenticity ofthis digital certificate anytime in the future even after the originalcertificate has expired. This process is called LTV (long termvalidation). This can ensure the integrity of the document and the videosignatures long after the current certificate has expired protecting theusers and signers.

At step 150, the process can include storing the hash value of therecorded signing video along with a link pointing to video. The systemcan also store credentials of each signer, for example: name, IPaddress, email address, cell phone number, date and time of the signing(e.g., as GST). In some implementations, the signer credentials can becaptured from a browser and from signer profiles.

The system can then create a blockchain to track future changes to thebundle and the video. Generally, a blockchain contains a hash linkedlist. If for some reason, for example, the video is changed, then thenew hash (for the changed video) will not match the hash value of theoriginal video (at time the video was created); this can signal thesigning process as being “tampered”. In some implementations, the systemcan alert, e.g., set and/or send a red flag if the hash value is alteredor indicate as safe if the hash value matches.

In some implementations, the system can generate an automatic auditreport after each signing by which the following are recorded in theaudit report, as shown in FIG. 16.

These features improve significantly technologies for digital recordsmanagement, tracking, and authentication, and technologies forcollaboration and authentication of documentation.

The systems and methods of the present disclosure can also be used inother fields, for example, video hashing and storing on a blockchain cangive a universal appeal for both individual and corporate recordkeeping. This can also be used for construction sites, surveyors' video,vigilance, security, etc., and having it hashed makes sure the contentsare not tampered with. It can also be used to check authenticity ofpirated audio/video contents. This has broad appeal where an event ofany kind can be record as a video and then stored with blockchain assecurity by itself or attached to another content like a document or toanother video. For example, if video #1 is tampered one cannot reachvideo #2 in the block chain.

System Architecture

The example of the present disclosure shown in the flow of FIG. 1 can beimplemented using the exemplary hardware and system shown in FIG. 2 andFIG. 3. FIG. 2 shows an exemplary high-level backend topology 200 ofservers used, and it can be, e.g., webserver coupled to database server,etc. For example, the backend can include a public network segment 202interfacing with a public network, such as the Internet, a privatenetwork segment 208, and a database internal network segment 210. Insome implementations, the backend can also include one or more virtualmachine banks and storage banks. The backend can also include firewallsincluding primary and secondary firewalls. The front-end hardware (notshown in FIG. 2) can include the user device and all the technicaldetail and components that come with it. These include, for example,tablets, phones, computers and all desktop (all browsers).

FIG. 3 illustrates an exemplary overall platform 300 in which variousembodiments and process steps disclosed herein can be implemented. Inaccordance with various aspects of the disclosure, an element (forexample, a host machine or a microgrid controller), or any portion of anelement, or any combination of elements can be implemented with aprocessing system 314 that includes one or more processing circuits 304.Processing circuits 304 can include micro-processing circuits,microcontrollers, digital signal processing circuits (DSPs), fieldprogrammable gate arrays (FPGAs), programmable logic devices (PLDs),state machines, gated logic, discrete hardware circuits, and othersuitable hardware configured to perform the various functionalitiesdescribed throughout this disclosure. That is, the processing circuit304 can be used to implement any one or more of the various embodiments,systems, algorithms, and processes described above. In some embodiments,the processing system 314 can be implemented in a server. The server canbe local or remote, for example in a cloud architecture.

In the example of FIG. 3, the processing system 314 can be implementedwith a bus architecture, represented generally by the bus 302. The bus302 can include any number of interconnecting buses and bridgesdepending on the specific application of the processing system 314 andthe overall design constraints. The bus 302 can link various circuitsincluding one or more processing circuits (represented generally by theprocessing circuit 304), the storage device 305, and a machine-readable,processor-readable, processing circuit-readable or computer-readablemedia (represented generally by a non-transitory machine-readable medium306). The bus 302 can also link various other circuits such as timingsources, peripherals, voltage regulators, and power management circuits,which are well known in the art, and therefore, will not be describedany further. The bus interface 308 can provide an interface between bus302 and a transceiver 310. The transceiver 310 can provide a means forcommunicating with various other apparatus over a transmission medium.Depending upon the nature of the apparatus, a user interface 312 (e.g.,keypad, display, speaker, microphone, touchscreen, motion sensor) canalso be provided.

The processing circuit 304 can be responsible for managing the bus 302and for general processing, including the execution of software storedon the machine-readable medium 306. The software, when executed byprocessing circuit 304, causes processing system 314 to perform thevarious functions described herein for any apparatus. Machine-readablemedium 306 can also be used for storing data that is manipulated byprocessing circuit 304 when executing software.

One or more processing circuits 304 in the processing system can executesoftware or software components. Software shall be construed broadly tomean instructions, instruction sets, code, code segments, program code,programs, subprograms, software modules, applications, softwareapplications, software packages, routines, subroutines, objects,executables, threads of execution, procedures, functions, etc., whetherreferred to as software, firmware, middleware, microcode, hardwaredescription language, or otherwise. A processing circuit can perform thetasks. A code segment can represent a procedure, a function, asubprogram, a program, a routine, a subroutine, a module, a softwarepackage, a class, or any combination of instructions, data structures,or program statements. A code segment can be coupled to another codesegment or a hardware circuit by passing and/or receiving information,data, arguments, parameters, or memory or storage contents. Information,arguments, parameters, data, etc. can be passed, forwarded, ortransmitted via any suitable means including memory sharing, messagepassing, token passing, network transmission, etc.

Various aspects have been presented in terms of systems that can includeseveral components, modules, and the like. It is to be understood andappreciated that the various systems can include additional components,modules, etc. and/or can not include all the components, modules, etc.discussed in connection with the figures. A combination of theseapproaches can also be used. The various aspects disclosed herein can beperformed on electrical devices including devices that utilize touchscreen display technologies and/or mouse-and-keyboard type interfaces.Examples of such devices include computers (desktop and mobile), smartphones, personal digital assistants (PDAs), and other electronic devicesboth wired and wireless.

In addition, the various illustrative logical blocks, modules, andcircuits described in connection with the aspects disclosed herein canbe implemented or performed with a general purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor can be a microprocessor,but in the alternative, the processor can be any conventional processor,controller, microcontroller, or state machine. A processor can also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

Operational aspects disclosed herein can be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumknown in the art. An exemplary storage medium is coupled to theprocessor such the processor can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium can be integral to the processor. The processor and the storagemedium can reside in an ASIC. The ASIC can reside in a user terminal. Inthe alternative, the processor and the storage medium can reside asdiscrete components in a user terminal.

Furthermore, the one or more versions can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedaspects. Non-transitory computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disk (CD), digitalversatile disk (DVD), BluRay™ . . . ), smart cards, solid-state devices(SSDs), and flash memory devices (e.g., card, stick). Of course, thoseskilled in the art will recognize many modifications can be made to thisconfiguration without departing from the scope of the disclosed aspects.

To the extent the embodiments disclosed herein include or operate inassociation with memory, storage, and/or computer readable media, thenthat memory, storage, and/or computer readable media are non-transitory.Accordingly, to the extent that memory, storage, and/or computerreadable media are covered by one or more claims, then that memory,storage, and/or computer readable media is only non-transitory.

Sample User Interfaces

FIGS. 4 to 17 show exemplary user interfaces of the present disclosure.For example, FIG. 4 shows an exemplary user interface of a home screenshown to a user after logging into the system of the present disclosure.The user can select 402 to create a new document to be signed or select404 to create a new document using a template, or select 406 to create anew document template. At 408, the system can indicate how manydocuments are waiting for action from the user.

After 404 or 406 has been selected, the system can show user interface500, as shown in FIG. 5, to facilitate creating a bundle. At 502, theuser can upload, or drag and drop, document(s).

FIG. 6 shows an exemplary bundle of documents, e.g., that have beenloaded, opened so that the user can indicate the locations or markers(e.g., 604) where signatures are needed, and by which signers. In someimplementations, the user can select Recipients 602 to see a list ofpeople to choose from. The list can be created manually earlier orimported from contact lists earlier.

FIG. 7 shows an exemplary user interface 700 to create a documenttemplate. FIG. 8 shows an exemplary template being created. FIG. 9 is anexemplary user interface 900 showing a directory (or folder) 902 oftemplates created by the user. The user can then select a template for abundle.

FIG. 10A shows an exemplary user interface 1000A for managing bundle ordocuments. Fr example, selecting 1002 lists documents with actions“waiting for you” (the user) to act on, for example, to open and review,or to sign. FIG. 10B shows list of bundles needing actions sent by aspecific participant 1010.

FIG. 10C shows an exemplary activity history of a bundle, e.g., whencreated and by who, when sent by who, when viewed by who, and so on. Insome embodiments, the activity can be stored in and retrieved from ablockchain.

FIGS. 11A and 11B show exemplary user interfaces 1100A and 1100B showingbundle with actions “waiting for others” (other users) to act on. FIGS.11C and 11D show exemplary user interfaces 1100C and 1100D for creatingand sending reminders to selected users.

FIG. 12 shows an exemplary user interface 1200 of a directory ofdocument signed. FIG. 13 shows an exemplary user interface cancelled ordeclined.

Turning to FIG. 14, an example user interface 1400 of a document signingvideo conference collaboration having a multiple of participants. Insome implementations, any and all participants can witness any and allsignings. This feature improves significantly the technologies forcollaboration and authentication of documentation.

FIG. 15 shows an exemplary user interface 1500 for inviting other usersto join a video conference to sign document(s). The invitation can bespontaneous.

As shown in FIG. 16, once a document has been signed by allparticipants, the system can generate a hash function of the recordedvideo. The hashed value can be displayed, for example, at the bottom ofthe last page, and stored as part of the digital signing on thedocument.

FIG. 17 shows an exemplary user interface 1700 of bundle directory,where the hash value can be displayed. This can indicate that thedocument was signed with video conferencing. It was recorded with a hashvalue and stored in a blockchain.

It should also be noted that all features, elements, components,functions, and steps described with respect to any embodiment providedherein are intended to be freely combinable and substitutable with thosefrom any other embodiment. If a certain feature, element, component,function, or step is described with respect to only one embodiment, thenit should be understood that that feature, element, component, function,or step can be used with every other embodiment described herein unlessexplicitly stated otherwise. This paragraph therefore serves asantecedent basis and written support for the introduction of claims, atany time, that combine features, elements, components, functions, andsteps from different embodiments, or that substitute features, elements,components, functions, and steps from one embodiment with those ofanother, even if the following description does not explicitly state, ina particular instance, that such combinations or substitutions arepossible. It is explicitly acknowledged that express recitation of everypossible combination and substitution is overly burdensome, especiallygiven that the permissibility of each and every such combination andsubstitution will be readily recognized by those of ordinary skill inthe art.

While the embodiments are susceptible to various modifications andalternative forms, specific examples thereof have been shown in thedrawings and are herein described in detail. It should be understood,however, that these embodiments are not to be limited to the particularform disclosed, but to the contrary, these embodiments are to cover allmodifications, equivalents, and alternatives falling within the spiritof the disclosure. Furthermore, any features, functions, steps, orelements of the embodiments can be recited in or added to the claims, aswell as negative limitations that define the inventive scope of theclaims by features, functions, steps, or elements that are not withinthat scope.

It is to be understood that this disclosure is not limited to theparticular embodiments described herein, as such may, of course, vary.It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting.

As used herein, the term “and/or” placed between a first entity and asecond entity means one of (1) the first entity, (2) the second entity,and (3) the first entity and the second entity. Multiple entities listedwith “and/or” should be construed in the same manner, i.e., “one ormore” of the entities so conjoined. Other entities may optionally bepresent other than the entities specifically identified by the “and/or”clause, whether related or unrelated to those entities specificallyidentified. Thus, as a non-limiting example, a reference to “A and/orB,” when used in conjunction with open-ended language such as“comprising” can refer, in one embodiment, to A only (optionallyincluding entities other than B); in another embodiment, to B only(optionally including entities other than A); in yet another embodiment,to both A and B (optionally including other entities). These entitiesmay refer to elements, actions, structures, steps, operations, values,and the like.

What is claimed is:
 1. A computer-implemented method for a blockchain,the method comprising: generating a hash value for a smart contract anda file containing digital contents; storing the file, the smart contractand the hash value; and updating a blockchain including the file, thesmart contract and the hash value.
 2. The computer-implemented method ofclaim 1 further comprises: receiving an updated copy of the blockchain;verifying a hash value in the updated copy of the blockchain; and if thehash value does not match the stored hash value, determine that theupdated copy of the blockchain contains at least one of a tempered copyof the smart contract or a tampered digital contents therebyinvalidating a contract integrity.
 3. The computer-implemented method ofclaim 1, wherein the file comprises video content.
 4. Thecomputer-implemented method of claim 1, wherein the file comprises audiocontent.